Using mirror indicators to determine whether to mirror tracks in a data set in a primary volume mirrored to a secondary volume

ABSTRACT

Provided are a computer program product, system, and method for using mirror indicators to determine whether to mirror tracks in a data set in a primary volume mirrored to a secondary volume. A table is read. The table is maintained by a primary controller managing the primary volume that includes a mirror indicator for each of a plurality of tracks in at least one data set configured in the primary volume indicating whether a track is to be mirrored to the secondary volume. Record sets are read from a cache of the primary controller for the tracks in primary volume having the mirror indicators in the table indicating that the track is to be mirrored. The write data in the read record sets is applied to tracks in the secondary volume mirroring the tracks in the primary volume

BACKGROUND OF THE INVENTION 1. Field of the Invention

The present invention relates to a computer program product, system, andmethod for using mirror indicators to determine whether to mirror tracksin a data set in a primary volume mirrored to a secondary volume.

2. Description of the Related Art

In certain computing environments, multiple host systems may configuredata sets in volumes configured in a storage system, such asinterconnected storage devices, e.g., a Direct Access Storage Device(DASD), Redundant Array of Independent Disks (RAID), Just a Bunch ofDisks (JBOD), etc. Data sets are comprised of extents, which maycomprise any grouping of tracks and data storage units. The Z/OS®operating system from International Business Machines Corporation(“IBM”) has a Volume Table of Contents (VTOC) to provide information ondata sets of extents configured in the volume, where the VTOC indicatesthe location of tracks, extents, and data sets for a volume in storage.

Disaster recovery systems typically address two types of failures, asudden catastrophic failure at a single point in time or data loss overa period of time. In the second type of gradual disaster, updates tovolumes may be lost. To assist in recovery of data updates, a copy ofdata may be provided at a remote location. Such dual or shadow copiesare typically made as the application system is writing new data to aprimary storage device. Different copy technologies may be used formaintaining remote copies of data at a secondary site, such asInternational Business Machine Corporation's (“IBM”) Extended RemoteCopy (XRC), Coupled XRC (CXRC), Global Copy, and Global Mirror Copy. Indata mirroring systems, data is maintained in volume pairs. A volumepair is comprised of a volume in a primary storage device and acorresponding volume in a secondary storage device that includes anidentical copy of the data maintained in the primary volume. Primary andsecondary control units, also known as storage controllers or enterprisestorage servers, may be used to control access to the primary andsecondary storage devices. In peer-to-peer remote copy operations(PPRC), multiple primary control units may have source/target pairs,i.e., volume pairs, included in consistency groups so that data copiedto target volumes by the different primary control units maintains dataconsistency.

When establishing a mirror copy relationship, the administrator may setup copy relationship between volumes in a session that may be groupedaccording to Logical Subsystem (LSS), where there may be multiple LSSs,each grouping multiple volumes, and where the LSSs are assigned to onesession. Data consistency may be maintained among the mirror copyoperations between the volumes in the LSSs assigned to a session.

There is a need in the art for improved techniques for controlling datamirroring operations.

SUMMARY

Provided are a computer program product, system, and method for usingmirror indicators to determine whether to mirror tracks in a data set ina primary volume mirrored to a secondary volume. A table is read. Thetable is maintained by a primary controller managing the primary volumethat includes a mirror indicator for each of a plurality of tracks in atleast one data set configured in the primary volume indicating whether atrack is to be mirrored to the secondary volume. Record sets are readfrom a cache of the primary controller for the tracks in primary volumehaving the mirror indicators in the table indicating that the track isto be mirrored. The write data in the read record sets is applied totracks in the secondary volume mirroring the tracks in the primaryvolume

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates an embodiment of a mirror copy storage environment.

FIG. 2 illustrates an embodiment of a volume table entry.

FIG. 3 illustrates an embodiment of a reference table entry.

FIG. 4 illustrates an embodiment of a record set.

FIG. 5 illustrates an embodiment of operations to generate a referencetable.

FIG. 6 illustrates an embodiment of operations to update the referencetable when allocating tracks to a data set in a mirror volume.

FIG. 7 illustrates an embodiment of operations to update the referencetable when deallocating a track from a data set.

FIG. 8 illustrates an embodiment of operations to process a write to atrack in the mirrored primary volume.

FIG. 9 illustrates an embodiment of operations to mirror tracks from theprimary volume to the secondary volume.

FIG. 10 illustrates an embodiment of operations to process a suspend orterminate of the mirror copy relationship.

FIG. 11 illustrates an embodiment of operations to update changes to thereference table.

FIG. 12 illustrates a computing environment in which the components ofFIG. 1 may be implemented.

DETAILED DESCRIPTION

Data mirror products are designed to copy full volumes from a primary toa secondary site. However, the customer may not want to copy certaindata sets or tracks within a data set, and copying a full volume wouldmove non-essential data sets prior to initiating the data mirror.Described embodiments allow a user to specify data sets and tracks in adata set to mirror in a user data set mirror list that is used togenerate a reference table to indicate which data sets and tracks in aprimary volume are mirrored, so that only those indicated data sets andtracks are mirrored. A data set mover at the secondary site may use thereference table to determine which tracks or record sets in the primarycontroller cache to copy to the secondary volume in the mirror copyrelationship. This allows the user to specify with fine grain controldata sets and tracks within a data set to include in the mirror copy.

FIG. 1 illustrates an embodiment of a mirror copy computing environmenthaving a primary controller 100 a managing access to primary volumes 102a in a primary storage 104 a at a primary site 106 a. A system datamover 108 may manage the mirroring of data in the primary volumes 102 ato secondary volumes 102 b in a secondary storage 104 b managed by asecondary controller 100 b at a secondary site 106 b. The system datamover 108 and primary controller 100 a communicate over a network 110.The primary 100 a and secondary 100 b controllers communicate with thestorages 104 a, 104 b, respectively, over connections 112 a, 112 b andthe system data mover 108 may connect to the secondary controller 100 bover connection 112 c. The connections 112 a, 112 b, 112 c may comprisea direct connection line, a network, wireless connection, etc. Infurther embodiments, the system data mover 108 may be implemented in thesecondary controller 100 b or a separate virtual or hardware system.

The controllers 100 a, 100 b manage access to data sets 114 a, 114 bconfigured in the primary 102 a and secondary 102 b volumes,respectively. A data set 114 a, 114 b comprises a collection of dataintended to be stored in a same logical allocation of data, such as datafrom a single application, user, enterprise, etc. A data set 114 a, 114b may be comprised of separate files or records, or comprise a singlefile or record. Each record or file in the data set may be comprised ofextents of data. The data sets 114 a, 114 b may comprise indexed datasets that are indexed according to a primary key that is used to locaterecords in the data set 114 a, 114 b or unindexed.

The primary 106 a and secondary 106 b sites may be at remote orproximate geographical locations, such as in a same building, same city,same state, same country, different countries, or any other regional,national, nautical, or planetary boundaries, etc.

The primary 100 a and secondary 100 b controllers each include a systemmemory 116 a, 116 b including an operating system 118 a, 118 b having avolume manager 120 a, 120 b to manage the storage of data sets 114 a,114 b in the volumes 102 a, 102 b. The operating system 118 a, 118 b maycomprise an operating such as the IBM z/OS® operating system or otheroperating systems. (IBM and z/OS are trademarks of IBM worldwide).

Each volume 102 a, 102 b includes a volume table 200 a, 200 b havinginformation on the volume 104 to which it pertains, including a mappingof tracks and extents of tracks to data sets 102. The volume table 200a, 200 b may be stored in the volume 102 a, 102 b, such as in the firstfew records of the volume, i.e., starting at the first track in thevolume 104. In IBM z/OS operating system implementations, the volumetable 200 a, 200 b may comprise a volume table of contents (VTOC). Thevolume tables 200 a, 200 b may comprise contiguous space data set havingcontiguous tracks or physical addresses in the storages 104 a, 104 b. Inalternative embodiments, the volume table 200 a, 200 b may comprise afile allocation table stored separately from the volume 102 a, 102 b.

The controllers 100 a, 100 b may maintain copies of the volume tables200 a, 200 b to use to manage the data sets 114 a, 114 b in the volumes200 a′, 200 b′ in their respective memory 116 a, 116 b. In z/OSimplementations, the volume table 200 a, 200 b, e.g., VTOC, may includeinformation on locations of data sets 114 a, 114 b in the volumes 102 a,102 b, such as a mapping of extents in the data set to storage locationsin the volume. In alternative embodiments, the volume tables 200 a, 200b may comprise other types of file allocation data structures thatprovide a mapping of data to storage locations, either logical and/orphysical storage locations. In this way, the volume table 200 a, 200 bprovides a mapping of tracks or extents to data sets 1114 a, 114 b inthe volumes 102 a, 102 b. In further embodiments, the volume tables 200a, 200 b may include a volume name (VOLSER) and data set recordsindicating data sets having extents configured in the volume 104. Eachdata set record in a volume table may have information for each data set102 in a volume 104, including the one or more extents assigned to thedata set 102. The data sets 114 a, 114 b may be variable size data setsor fixed sized data sets.

The operating systems 118 a, 118 b further include an Input/Outputsupervisor 122 a, 122 b comprising a driver to manage the disk cachingand access operations for the volumes 102 a, 102 b configured in theprimary 104 a and secondary 104 b storages, respectively. Further theI/O supervisor 122 a may manage the storage of record sets 400 in acache 124 a to cache data for the primary volumes 102 a. The secondarycontroller 100 b has a cache 124 b to cache data for the secondaryvolumes 102 b. The operating system 118 a, 118 b may further include acopy manager 126 a, 126 b to manage mirror copy operations between theprimary 100 a and secondary 100 b controllers. The system data mover 108would further have information on mirror copy relationships 128established between the primary volumes 102 a and secondary volumes 102b, which may be created by the copy manager 126 a. The I/O supervisor122 a creates record sets 400 in the cache 124 b for track data tomirror to the secondary volume 102 b.

The volume manager 120 a may further generate a reference table 300 toprovide fine grain control on which tracks in data sets 114 a are to bemirrored to the secondary volume 102 b to allow for only a subset oftracks in the data sets 114 a to be mirrored to the secondary volume 102b. The reference table 300 may be stored at contiguous physicallocations in the primary storage 104 a with respect to the volume table200 a in the primary volume 102 a, such as an extension of the volumetable 200 a. A copy of the reference table 300′ may be maintained in thememory 116 a.

The copy manager 126 a or other component may receive a data set mirrorlist 130 from a user indicating for a primary volume 102 a in a mirrorcopy relationship 128 the data sets 114 a and tracks within data sets toinclude in the mirror copy. The reference table 300 is generated basedon the data set mirror list 130 from a user or administrator to indicatethe data sets or tracks that are to be mirrored to the secondary volume102 b.

The storages 104 a, 104 b may comprise one or more storage devices knownin the art, such as a solid state storage device (SSD) comprised ofsolid state electronics, NAND storage cells, EEPROM (ElectricallyErasable Programmable Read-Only Memory), flash memory, flash disk,Random Access Memory (RAM) drive, storage-class memory (SCM), PhaseChange Memory (PCM), resistive random access memory (RRAM), spintransfer torque memory (STM-RAM), conductive bridging RAM (CBRAM),Non-Volatile Dual In-line Memory Module (NVDIMM), Static Random AccessMemory (SRAM), magnetic hard disk drive, optical disk, tape, etc. Thestorage devices may further be configured into an array of devices, suchas Just a Bunch of Disks (JBOD), Direct Access Storage Device (DASD),Redundant Array of Independent Disks (RAID) array, virtualizationdevice, etc. Further, the storages 104 a, 104 b may compriseheterogeneous storage devices from different vendors or from the samevendor.

The memory 116 a, 116 b may comprise suitable volatile or non-volatilememory devices for a system or main memory, including those memory classdevices described above with respect to the storages 104 a, 104 b.

The primary controller 100 a, secondary controller 100 b, and systemdata mover 108 may communicate over a network 132, such as a Local AreaNetwork (LAN), Storage Area Network (SAN), Wide Area Network (WAN),peer-to-peer network, wireless network, etc. Alternatively, theconnection 114 may comprise bus interfaces, such as a PeripheralComponent Interconnect (PCI) bus or serial interface.

FIG. 2 illustrates an arrangement of information maintained in aninstance of a volume table 200 _(i) for one volume 102 a, 102 b. Thevolume table instance 200 _(i) includes a volume name 202, also known asa volume serial number, e.g., a VOLSER, that provides a uniqueidentifier of the volume. The volume name 202 may be included in thename of the volume table 200 _(i) in the volume 104 _(i). The volumetable 200 _(i) instance further includes one or more data set records204 ₁ . . . 204 _(n) indicating data sets having extents configured inthe volumes 102 a, 102 b represented by the volume table 200 _(i). Thevolume table 200 _(i) may further include additional metadata on thevolume 102 a, 102 b configuration.

FIG. 3 illustrates an embodiment of a reference table entry 300 i in thereference table 300 for each track configured in a volume 102 a, andincludes a logical subsystem (LSS) 302 including the track, comprisinglogical functions of a storage controller that allow one or more hostI/O interfaces to access a set of devices; a channel connection address(CCA) 304, which comprises an I/O address that uniquely identifies anI/O device to the channel during an I/O operation; a volume name 306,such as a volume serial number (VOLSER); a track identifier 308, such asa, cylinder number (CC) and head number (HH); a data set name 310 of thedata set including the track 308; and a mirror indicator 312 indicatingwhether the track 308 is to be mirrored to the secondary volume 102 b.

FIG. 4 illustrates an embodiment of a record set 400 _(i) instance,including the LSS 402, volume 404, and track identifier 406 of a track,track data 408, such as write data, and a copied flag 410 indicatingwhether the record set 400 _(i) was copied. The copied flag 410 may beimplemented in the hardware of the cache 124 a, such as in the cacheline.

FIG. 5 illustrates an embodiment of operations performed by the volumemanager 120 a to generate a reference table 300 for the volume table 200a, which may be created when the volume 102 a is configured in theprimary storage 104 a. Upon initiating (at block 500) the operation toinitialize the reference table 300, the volume manager 120 for eachtrack in the created volume, creates (at block 502) a reference tableentry 300, indicating the LSS 302, channel connection address (CCA),volume name 306, and track number 308, leaves the data set name 310empty, and sets the mirror indicator to indicate no mirroring. In thisway, the track is assigned to the volume 306 but not yet allocated foruse or mirroring.

When creating a reference table for a mirror copy that will perform aninitial full copy of the primary volume 102 a, the data set name 310 andmirror indicators 312 for all the tracks may be set to indicate copyingto cause the system data mover 108 to perform a full copy of the entireprimary volume 102 a to the secondary volume 102 b.

FIG. 6 illustrates an embodiment of operations performed by the volumemanager 120 a to allocate a data set and tracks to a data set, in aninitial or supplemental allocation, based on a data set mirror list 130provided by a user to indicate which data sets and tracks to subject tomirroring. Upon allocating one or more data sets and tracks (at block600), the volume manager 120 a updates (at block 602) the volume table200 a to indicate the added data sets, tracks, or extents of tracks. Foreach track in a data set being allocated, the volume manager 120 aupdates (at block 604) the reference table entries 300 _(i) for theallocated tracks in the volume 306 to indicate the data set name inwhich the track is allocated in field 310. For each allocated trackspecified in a received user data set list to be mirrored, set (at block606) the mirror indicator 312 to indicate mirroring. The mirrorindicator 312 indicates no mirroring for allocated tracks not specifiedto mirror. The data set mirror list 130 may specify individual tracks ofa data set 114 a to mirror or may specify to mirror all tracks in a dataset 114 a. The allocation may be of an entire data set 114 a or to addtracks to an existing data set 114 a.

In certain embodiments, the user specified data set mirror list 130 mayindicate to mirror tracks including metadata and configurationinformation for a volume, including the volume table 200 a, referencetable 300, and other configuration information for a volume 102 a. Thisensures mirror copy protection of critical system files and information.

FIG. 7 illustrates an embodiment of operations performed by the volumemanager 120 a to deallocate or remove a data set 114 a or track in adata set 114 a from the primary volume 102 a. Upon deallocating (atblock 700) a data set or track in a data set, the volume manager 120 aupdates (at block 702) the volume table 200 a to indicate the track isremoved from the data set. The mirror indicator 312 is set (at block704) to indicate no mirroring in the reference table entry 300 _(i) forthe deallocated track and the data set name 310 for the track 308 beingdeallocated is cleared (at block 706). This setting of the mirrorindicator 312 and clearing of the data set name 310 will cause thesecondary controller 100 b to remove data for the track from themirrored secondary volume 102 b. The deallocation may involvedeallocating an entire data set 114 a and all tracks therein or todeallocate or remove specific tracks from a data set 114 a.

FIG. 8 illustrates an embodiment of operations performed by the I/Osupervisor 122 a to process a write to a track in a primary volume 102 athat is mirrored to a secondary volume 102 b. Upon receiving (at block800) the write, the I/O supervisor 122 a reads (at block 802) the entry300 _(i) for the written track in the reference table 300. If (at block804) the mirror indicator 312 for the updated track indicates mirroring,then the I/O supervisor 122 a adds (at block 806) a record set 400 _(i)to the cache 124 a for the updated track including the LSS 402, volume404, track identifier 406, the write data 408 for the track; and setsthe copied flag 410 to indicate that the track data has not been copied.

FIG. 9 illustrates an embodiment of operations performed by the systemdata mover 108 to mirror tracks in record sets 400 in the primary cache124 a to the secondary volume 102 a. Upon initiating (at block 900) theoperation to mirror data, the system data mover 108 reads (at block 902)the reference table 300 for a primary volume 102 a in a mirror copyrelationship 128. If (at block 904) there are tracks in the referencetable 300 having the mirror indicator 312 indicating to mirror data,then the system data mover 108 reads (at block 906) the primary volume102 a cache 124 a to determine whether there are record sets 400 for thedetermined tracks to mirror having the copied flag 410 indicating therecord set 400 _(i) has not yet been copied. If (at block 908) there aredetermined record sets 400 to copy, then the system data mover 108 reads(at block 910) each of the determined record sets 400 _(i) having an LSS402 and volume 404 for the primary volume 102 a in the mirror copyrelationship 128 and applies (at block 912) the data for the tracks inthe read determined record sets 400 to the corresponding tracks in themirrored secondary volume 102 b in the mirror copy relationship 128. Thecopied flag 410 in the read record set 400 _(i) in the cache 124 a isset (at block 914) to indicate the record set 400 _(i) has been copied.

If (at block 904) there are no tracks in the reference table 300 havingthe mirror indicator 312 indicating to mirror data or if (at block 908)there are no record sets 400 _(i) to copy, i.e., having the copied flag410 indicating already copied, then control ends without reading andmirroring data.

With the described embodiments, the system data mover 108 only mirrorsthe record sets 400 in the cache 124 a that are indicated to be mirroredin the mirror indicator 312 of the reference table entry 300 _(i) forthe track being considered. Tracks or record sets that are not indicatedto be mirrored are then left in the cache 124 a and not mirrored. Thisallows for fine-grain control of the tracks of a primary volume 102 a ina mirror copy relationship 128 that will be subject to mirroring, sothat only those tracks of a data set 114 a are specified to be mirroredare mirrored, and tracks in a data set 114 a in a volume 102 a to mirrorthat have not been specified to mirror will not be mirrored to store inthe secondary storage 104 b.

FIG. 10 illustrates an embodiment of operations performed by the systemdata mover 108 to process a suspend or terminate of a mirror copyrelationship 128. Upon initiating (at block 1000) the suspension ortermination of a mirror copy relationship 128 for a primary 102 a andsecondary 102 b volumes, the system data mover 108 reads (at block 1002)the reference table 300 for the primary volume 1002. If (at block 1004)the reference table 300 has entries with tracks 308 indicated as deletedfrom the primary volume 102 a, which is indicated by the entry 300,having no data set name 310, then the system data mover 108 invalidates(at block 1006) tracks/data sets in the secondary volume indicated asdeleted, such as by writing all 0s to the track.

With the embodiment of FIG. 10, once a mirror copy relationship 128 issuspended or terminated, the secondary volume 102 b mirror copy is madeconsistent with the current state of the primary volume 102 a beingmirrored by removing tracks/data sets from the secondary volume 102 bremoved from the primary volume 102 a.

FIG. 11 illustrates an embodiment of operations performed by the volumemanager 120 a or 120 b upon detecting changes to the configurationand/or addressing at the secondary volume 102 b, such as a change in thelogical subsystem or channel connect address. Upon detecting (at block1100) a change to the configuration and/or addressing, the fields 302and/or 304 in the entries 300 _(i) of the reference table 300 areupdated to reflect the changes, so that the system data mover 108 candetermine from the updated reference table 300 the secondary volume 102a locations to be updated with the updated track data.

In FIGS. 3-8, operations described as performed by the volume manager120 a and the I/O supervisor 122 a may be performed all or in part byanother component. In FIGS. 9-10, operations described as performed bythe system data mover 108 may be performed all or in part by anothercomponent, such as the copy manager 126 a.

The reference characters used herein, such as i and n used herein todenote a variable number of instances of an element, which may representthe same or different values, and may represent the same or differentvalue when used with different or the same elements in differentdescribed instances.

The present invention may be a system, a method, and/or a computerprogram product. The computer program product may include a computerreadable storage medium (or media) having computer readable programinstructions thereon for causing a processor to carry out aspects of thepresent invention.

The computer readable storage medium can be a tangible device that canretain and store instructions for use by an instruction executiondevice. The computer readable storage medium may be, for example, but isnot limited to, an electronic storage device, a magnetic storage device,an optical storage device, an electromagnetic storage device, asemiconductor storage device, or any suitable combination of theforegoing. A non-exhaustive list of more specific examples of thecomputer readable storage medium includes the following: a portablecomputer diskette, a hard disk, a random access memory (RAM), aread-only memory (ROM), an erasable programmable read-only memory (EPROMor Flash memory), a static random access memory (SRAM), a portablecompact disc read-only memory (CD-ROM), a digital versatile disk (DVD),a memory stick, a floppy disk, a mechanically encoded device such aspunch-cards or raised structures in a groove having instructionsrecorded thereon, and any suitable combination of the foregoing. Acomputer readable storage medium, as used herein, is not to be construedas being transitory signals per se, such as radio waves or other freelypropagating electromagnetic waves, electromagnetic waves propagatingthrough a waveguide or other transmission media (e.g., light pulsespassing through a fiber-optic cable), or electrical signals transmittedthrough a wire.

Computer readable program instructions described herein can bedownloaded to respective computing/processing devices from a computerreadable storage medium or to an external computer or external storagedevice via a network, for example, the Internet, a local area network, awide area network and/or a wireless network. The network may comprisecopper transmission cables, optical transmission fibers, wirelesstransmission, routers, firewalls, switches, gateway computers and/oredge servers. A network adapter card or network interface in eachcomputing/processing device receives computer readable programinstructions from the network and forwards the computer readable programinstructions for storage in a computer readable storage medium withinthe respective computing/processing device.

Computer readable program instructions for carrying out operations ofthe present invention may be assembler instructions,instruction-set-architecture (ISA) instructions, machine instructions,machine dependent instructions, microcode, firmware instructions,state-setting data, or either source code or object code written in anycombination of one or more programming languages, including an objectoriented programming language such as Java, Smalltalk, C++ or the like,and conventional procedural programming languages, such as the “C”programming language or similar programming languages. The computerreadable program instructions may execute entirely on the user'scomputer, partly on the user's computer, as a stand-alone softwarepackage, partly on the user's computer and partly on a remote computeror entirely on the remote computer or server. In the latter scenario,the remote computer may be connected to the user's computer through anytype of network, including a local area network (LAN) or a wide areanetwork (WAN), or the connection may be made to an external computer(for example, through the Internet using an Internet Service Provider).In some embodiments, electronic circuitry including, for example,programmable logic circuitry, field-programmable gate arrays (FPGA), orprogrammable logic arrays (PLA) may execute the computer readableprogram instructions by utilizing state information of the computerreadable program instructions to personalize the electronic circuitry,in order to perform aspects of the present invention.

Aspects of the present invention are described herein with reference toflowchart illustrations and/or block diagrams of methods, apparatus(systems), and computer program products according to embodiments of theinvention. It will be understood that each block of the flowchartillustrations and/or block diagrams, and combinations of blocks in theflowchart illustrations and/or block diagrams, can be implemented bycomputer readable program instructions.

These computer readable program instructions may be provided to aprocessor of a general purpose computer, special purpose computer, orother programmable data processing apparatus to produce a machine, suchthat the instructions, which execute via the processor of the computeror other programmable data processing apparatus, create means forimplementing the functions/acts specified in the flowchart and/or blockdiagram block or blocks. These computer readable program instructionsmay also be stored in a computer readable storage medium that can directa computer, a programmable data processing apparatus, and/or otherdevices to function in a particular manner, such that the computerreadable storage medium having instructions stored therein comprises anarticle of manufacture including instructions which implement aspects ofthe function/act specified in the flowchart and/or block diagram blockor blocks.

The computer readable program instructions may also be loaded onto acomputer, other programmable data processing apparatus, or other deviceto cause a series of operational steps to be performed on the computer,other programmable apparatus or other device to produce a computerimplemented process, such that the instructions which execute on thecomputer, other programmable apparatus, or other device implement thefunctions/acts specified in the flowchart and/or block diagram block orblocks.

The flowchart and block diagrams in the Figures illustrate thearchitecture, functionality, and operation of possible implementationsof systems, methods, and computer program products according to variousembodiments of the present invention. In this regard, each block in theflowchart or block diagrams may represent a module, segment, or portionof instructions, which comprises one or more executable instructions forimplementing the specified logical function(s). In some alternativeimplementations, the functions noted in the block may occur out of theorder noted in the figures. For example, two blocks shown in successionmay, in fact, be executed substantially concurrently, or the blocks maysometimes be executed in the reverse order, depending upon thefunctionality involved. It will also be noted that each block of theblock diagrams and/or flowchart illustration, and combinations of blocksin the block diagrams and/or flowchart illustration, can be implementedby special purpose hardware-based systems that perform the specifiedfunctions or acts or carry out combinations of special purpose hardwareand computer instructions.

The computational components of FIG. 1, including the controllers 100 a,100 b, and system data mover 108 may be implemented in one or morecomputer systems, such as the computer system 1202 shown in FIG. 12.Computer system/server 1202 may be described in the general context ofcomputer system executable instructions, such as program modules, beingexecuted by a computer system. Generally, program modules may includeroutines, programs, objects, components, logic, data structures, and soon that perform particular tasks or implement particular abstract datatypes. Computer system/server 1202 may be practiced in distributed cloudcomputing environments where tasks are performed by remote processingdevices that are linked through a communications network. In adistributed cloud computing environment, program modules may be locatedin both local and remote computer system storage media including memorystorage devices.

As shown in FIG. 12, the computer system/server 1202 is shown in theform of a general-purpose computing device. The components of computersystem/server 1202 may include, but are not limited to, one or moreprocessors or processing units 1204, a system memory 1206, and a bus1208 that couples various system components including system memory 1206to processor 1204. Bus 1208 represents one or more of any of severaltypes of bus structures, including a memory bus or memory controller, aperipheral bus, an accelerated graphics port, and a processor or localbus using any of a variety of bus architectures. By way of example, andnot limitation, such architectures include Industry StandardArchitecture (ISA) bus, Micro Channel Architecture (MCA) bus, EnhancedISA (EISA) bus, Video Electronics Standards Association (VESA) localbus, and Peripheral Component Interconnects (PCI) bus.

Computer system/server 1202 typically includes a variety of computersystem readable media. Such media may be any available media that isaccessible by computer system/server 1202, and it includes both volatileand non-volatile media, removable and non-removable media.

System memory 1206 can include computer system readable media in theform of volatile memory, such as random access memory (RAM) 1210 and/orcache memory 1212. Computer system/server 1202 may further include otherremovable/non-removable, volatile/non-volatile computer system storagemedia. By way of example only, storage system 1213 can be provided forreading from and writing to a non-removable, non-volatile magnetic media(not shown and typically called a “hard drive”). Although not shown, amagnetic disk drive for reading from and writing to a removable,non-volatile magnetic disk (e.g., a “floppy disk”), and an optical diskdrive for reading from or writing to a removable, non-volatile opticaldisk such as a CD-ROM, DVD-ROM or other optical media can be provided.In such instances, each can be connected to bus 1208 by one or more datamedia interfaces. As will be further depicted and described below,memory 1206 may include at least one program product having a set (e.g.,at least one) of program modules that are configured to carry out thefunctions of embodiments of the invention.

Program/utility 1214, having a set (at least one) of program modules1216, may be stored in memory 1206 by way of example, and notlimitation, as well as an operating system, one or more applicationprograms, other program modules, and program data. Each of the operatingsystem, one or more application programs, other program modules, andprogram data or some combination thereof, may include an implementationof a networking environment. The components of the computer 1202 may beimplemented as program modules 1216 which generally carry out thefunctions and/or methodologies of embodiments of the invention asdescribed herein. The systems of FIG. 1 may be implemented in one ormore computer systems 1202, where if they are implemented in multiplecomputer systems 1202, then the computer systems may communicate over anetwork.

Computer system/server 1202 may also communicate with one or moreexternal devices 1218 such as a keyboard, a pointing device, a display1220, etc.; one or more devices that enable a user to interact withcomputer system/server 1202; and/or any devices (e.g., network card,modem, etc.) that enable computer system/server 1202 to communicate withone or more other computing devices. Such communication can occur viaInput/Output (I/O) interfaces 1222. Still yet, computer system/server1202 can communicate with one or more networks such as a local areanetwork (LAN), a general wide area network (WAN), and/or a publicnetwork (e.g., the Internet) via network adapter 1224. As depicted,network adapter 1224 communicates with the other components of computersystem/server 1202 via bus 1208. It should be understood that althoughnot shown, other hardware and/or software components could be used inconjunction with computer system/server 1202. Examples, include, but arenot limited to: microcode, device drivers, redundant processing units,external disk drive arrays, RAID systems, tape drives, and data archivalstorage systems, etc.

The terms “an embodiment”, “embodiment”, “embodiments”, “theembodiment”, “the embodiments”, “one or more embodiments”, “someembodiments”, and “one embodiment” mean “one or more (but not all)embodiments of the present invention(s)” unless expressly specifiedotherwise.

The terms “including”, “comprising”, “having” and variations thereofmean “including but not limited to”, unless expressly specifiedotherwise.

The enumerated listing of items does not imply that any or all of theitems are mutually exclusive, unless expressly specified otherwise.

The terms “a”, “an” and “the” mean “one or more”, unless expresslyspecified otherwise.

Devices that are in communication with each other need not be incontinuous communication with each other, unless expressly specifiedotherwise. In addition, devices that are in communication with eachother may communicate directly or indirectly through one or moreintermediaries.

A description of an embodiment with several components in communicationwith each other does not imply that all such components are required. Onthe contrary a variety of optional components are described toillustrate the wide variety of possible embodiments of the presentinvention.

When a single device or article is described herein, it will be readilyapparent that more than one device/article (whether or not theycooperate) may be used in place of a single device/article. Similarly,where more than one device or article is described herein (whether ornot they cooperate), it will be readily apparent that a singledevice/article may be used in place of the more than one device orarticle or a different number of devices/articles may be used instead ofthe shown number of devices or programs. The functionality and/or thefeatures of a device may be alternatively embodied by one or more otherdevices which are not explicitly described as having suchfunctionality/features. Thus, other embodiments of the present inventionneed not include the device itself.

The foregoing description of various embodiments of the invention hasbeen presented for the purposes of illustration and description. It isnot intended to be exhaustive or to limit the invention to the preciseform disclosed. Many modifications and variations are possible in lightof the above teaching. It is intended that the scope of the invention belimited not by this detailed description, but rather by the claimsappended hereto. The above specification, examples and data provide acomplete description of the manufacture and use of the composition ofthe invention. Since many embodiments of the invention can be madewithout departing from the spirit and scope of the invention, theinvention resides in the claims herein after appended.

1-23. (canceled)
 24. A computer program product for mirroring databetween a primary volume managed by a primary controller having a cacheand a secondary volume, wherein the computer program product comprises acomputer readable storage medium having program instructions embodiedtherewith, the program instructions executable by a processor to causeoperations, the operations comprising: in response to an allocation ofat least one data set to the primary volume, updating a table toindicate allocated tracks in the at least one data set allocated to theprimary volume and, for each allocated track of the allocated tracksindicated in the table that is specified to be mirrored to the secondaryvolume, setting a mirror indicator indicating that the allocated trackis to be mirrored to the secondary volume, wherein less than all of theallocated tracks indicated in the table are specified to be mirrored tothe secondary volume; reading record sets from the cache of the primarycontroller for tracks in the primary volume having mirror indicatorsindicating that the tracks are to be mirrored; and applying write datain the read record sets to tracks in the secondary volume mirroring thetracks in the primary volume according to mirror indicators for thetracks.
 25. The computer program product of claim 24, wherein the tablecomprises a reference table, further comprising: in response toconfiguring the primary volume in a primary storage, initializing thereference table including an entry for each track in a data set in theprimary volume including the mirror indicator for the track; and settingthe mirror indicator in each entry to indicate no mirroring for thetrack in the entry in response to initializing the reference table. 26.The computer program product of claim 24, wherein the operations furthercomprise: determining from the table at least one track that isindicated as being deallocated from the primary volume; and invalidatingthe determined at least one track indicated as being deallocated fromthe primary volume.
 27. The computer program product of claim 26,wherein the invalidating the tracks in the secondary volume is performedin response to an operation suspending a mirror copy between the primaryvolume and the secondary volume.
 28. The computer program product ofclaim 24, wherein the primary volume and the cache are at a primarysite, wherein the secondary volume is at a secondary site, wherein asystem data mover at the secondary site reads the table, reads therecord sets from the cache, and applies the write data in the readrecord sets to the tracks in the secondary volume for which the recordsets provide data.
 29. The computer program product of claim 24, whereinthe table comprises a reference table stored next to a volume table inthe primary volume, wherein the volume table provides information ondata sets and tracks allocated in the primary volume and the mirrorindicators for data sets and tracks indicated in the primary volume. 30.The computer program product of claim 24, wherein the table indicates alogical subsystem and a device address for each of the tracks in the atleast one data set, wherein the operations further comprise: determiningat least data set and the tracks having the logical subsystem and deviceaddress configured in the primary volume that were modified; andupdating at least one of the logical subsystem and the device address inthe table for each of the determined at least one data set and thetracks to reflect current settings for the at least one of the logicalsubsystem and the device address.
 31. A system in communication with aprimary controller, having a cache, managing access to a primary volumemirrored to a secondary volume, comprising: a processor; a computerreadable storage medium having program instructions that when executedby a processor performs operations, the operations comprising: inresponse to an allocation of at least one data set to the primaryvolume, updating a table to indicate allocated tracks in the at leastone data set allocated to the primary volume and, for each allocatedtrack of the allocated tracks indicated in the table that is specifiedto be mirrored to the secondary volume, setting i a mirror indicatorindicating that the allocated track is to be mirrored to the secondaryvolume, wherein less than all of the allocated tracks indicated in thetable are specified to be mirrored to the secondary volume; readingrecord sets from the cache of the primary controller for tracks in theprimary volume having mirror indicators indicating that the tracks areto be mirrored; and applying write data in the read record sets totracks in the secondary volume mirroring the tracks in the primaryvolume according to mirror indicators for the tracks.
 32. The computerprogram product of claim 31, wherein the table comprises a referencetable, further comprising: in response to configuring the primary volumein a primary storage, initializing the reference table including anentry for each track in a data set in the primary volume including themirror indicator for the track; and setting the mirror indicator in eachentry to indicate no mirroring for the track in the entry in response toinitializing the reference table.
 33. The system of claim 31, whereinthe operations further comprise: determining from the table at least onetrack that is indicated as being deallocated from the primary volume;and invalidating the determined at least one track indicated as beingdeallocated from the primary volume.
 34. The system of claim 33, whereinthe invalidating the tracks in the secondary volume is performed inresponse to an operation suspending a mirror copy between the primaryvolume and the secondary volume.
 35. The system of claim 31, wherein theprimary volume and the cache are at a primary site, wherein thesecondary volume is at a secondary site, wherein a system data mover atthe secondary site reads the table, reads the record sets from thecache, and applies the write data in the read record sets to the tracksin the secondary volume for which the record sets provide data.
 36. Thesystem of claim 31, wherein the table indicates a logical subsystem anda device address for each of the tracks in the at least one data set,wherein the operations further comprise: determining at least data setand the tracks having the logical subsystem and device addressconfigured in the primary volume that were modified; and updating atleast one of the logical subsystem and the device address in the tablefor each of the determined at least one data set and the tracks toreflect current settings for the at least one of the logical subsystemand the device address.
 37. A method for mirroring data between aprimary volume and a secondary volume, comprising: in response to anallocation of at least one data set to the primary volume, updating atable to indicate allocated tracks in the at least one data setallocated to the primary volume and, for each allocated track of theallocated tracks indicated in the table that is specified to be mirroredto the secondary volume, setting a mirror indicator a indicating thatthe allocated track is to be mirrored to the secondary volume, whereinless than all of the allocated tracks indicated in the table arespecified to be mirrored to the secondary volume; reading record setsfrom a cache of the primary controller for tracks in the primary volumehaving mirror indicators indicating that the tracks are to be mirrored;and applying write data in the read record sets to tracks in thesecondary volume mirroring the tracks in the primary volume according tomirror indicators for the tracks.
 38. The method of claim 37, whereinthe table comprises a reference table, further comprising: in responseto configuring the primary volume in a primary storage, initializing thereference table including an entry for each track in a data set in theprimary volume including the mirror indicator for the track; and settingthe mirror indicator in each entry to indicate no mirroring for thetrack in the entry in response to initializing the reference table. 39.The method of claim 37, further comprising: determining from the tableat least one track that is indicated as being deallocated from theprimary volume; and invalidating the determined at least one trackindicated as being deallocated from the primary volume.
 40. The methodof claim 37, wherein the invalidating the tracks in the secondary volumeis performed in response to an operation suspending a mirror copybetween the primary volume and the secondary volume.
 41. The method ofclaim 37, wherein the primary volume and the cache are at a primarysite, wherein the secondary volume is at a secondary site, wherein asystem data mover at the secondary site reads the table, reads therecord sets from the cache, and applies the write data in the readrecord sets to the tracks in the secondary volume for which the recordsets provide data.
 42. The method of claim 37, wherein the tableindicates a logical subsystem and a device address for each of thetracks in the at least one data set, further comprising: determining atleast data set and the tracks having the logical subsystem and deviceaddress configured in the primary volume that were modified; andupdating at least one of the logical subsystem and the device address inthe table for each of the determined at least one data set and thetracks to reflect current settings for the at least one of the logicalsubsystem and the device address.